18/02/2024 - 24/02/2024

20/02/2024 00:02

I'm currently trying to ping the MCH. I got rid of the ethernet splitter (network box, or whatever it's called) and directly connected the MCH to 'be'. Both ports are blinking, but not data is being transferred to the MCH as far as I'm aware.
These are the network settings I tried to use:

[root@dhcp-10-163-105-238 network-scripts]# cat ifcfg-enp5s0
#
# Connect to WaveDream Board
#
#TYPE=Ethernet
#BOOTPROTO=static
#IPADDR=192.168.248.251
#NETMASK=255.255.0.0
#IPV4_FAILURE_FATAL=no
#IPV6INIT=no
#IPV6_AUTOCONF=yes
#IPV6_DEFROUTE=yes
#IPV6_PEERDNS=yes
#IPV6_PEERROUTES=yes
#IPV6_FAILURE_FATAL=no
#NAME=enp5s0
#DEVICE=enp5s0
#ONBOOT=yes
#
# Connect to FE01
#
#DEVICE="enp5s0"
#NM_CONTROLLED="no"
#ONBOOT=yes
#TYPE=Ethernet
#BOOTPROTO=static
#IPADDR=10.0.0.2
#NETMASK=255.255.255.0
#
# Default Configuration
#
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp5s0
UUID=c7e67db0-b884-4b86-935e-483b1bbf52dc
DEVICE=enp5s0
ONBOOT=no

[root@dhcp-10-163-105-238 network-scripts]# cat ifcfg-enp5s0
#
# Connect to WaveDream Board
#
#TYPE=Ethernet
#BOOTPROTO=static
#IPADDR=192.168.248.251
#NETMASK=255.255.0.0
#IPV4_FAILURE_FATAL=no
#IPV6INIT=no
#IPV6_AUTOCONF=yes
#IPV6_DEFROUTE=yes
#IPV6_PEERDNS=yes
#IPV6_PEERROUTES=yes
#IPV6_FAILURE_FATAL=no
#NAME=enp5s0
#DEVICE=enp5s0
#ONBOOT=yes
#
# Connect to FE01
#
#DEVICE="enp5s0"
#NM_CONTROLLED="no"
#ONBOOT=yes
#TYPE=Ethernet
#BOOTPROTO=static
#IPADDR=10.0.0.2
#NETMASK=255.255.255.0
#
# Default Configuration
#
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp5s0
UUID=c7e67db0-b884-4b86-935e-483b1bbf52dc
DEVICE=enp5s0
ONBOOT=no

I tired pinging the MCH at it's factory default adresses but no luck:

ping 192.168.1.230
ping 192.168.1.231
ping 192.168.16.17
ping 192.168.1.41

ping 192.168.1.230
ping 192.168.1.231
ping 192.168.16.17
ping 192.168.1.41

The last one is just he address from Tim's notes. Here is the relevant part of ifconfig:

enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.0.1  netmask 255.255.255.0  broadcast 10.0.0.255
        inet6 fe80::f0f4:a75c:c399:9a9a  prefixlen 64  scopeid 0x20<link>
        ether 00:1b:21:59:59:a5  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 49  bytes 7659 (7.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xfbac0000-fbae0000

enp5s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.0.0.1  netmask 255.255.255.0  broadcast 10.0.0.255
        inet6 fe80::f0f4:a75c:c399:9a9a  prefixlen 64  scopeid 0x20<link>
        ether 00:1b:21:59:59:a5  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 49  bytes 7659 (7.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 16  memory 0xfbac0000-fbae0000

20/02/2024 00:36

I also tried connecting the ethernet ports of the MCH to our newest desktop, hoping it would automatically lease and IP from the MCH. This did not work even after restarting both the crate and the computer.

20/02/2024 00:57

I looked at the way we connected to the wavedream, and basically copy and pasted those network script settings into
/etc/sysconfig/networkscripts/ifcfg-enp5s0
so that it looked like this (effectively, more comments that are excluded here):

#
# Connect to MCH
#
TYPE=Ethernet
BOOTPROTO=static
IPADDR=192.168.1.1
NETMASK=255.255.0.0
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=enp5s0
DEVICE=enp5s0
ONBOOT=yes

#
# Connect to MCH
#
TYPE=Ethernet
BOOTPROTO=static
IPADDR=192.168.1.1
NETMASK=255.255.0.0
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=enp5s0
DEVICE=enp5s0
ONBOOT=yes

Then I was able to ping the MCH as in Tim's notes:

[root@dhcp-10-163-105-238 network-scripts]# ping 192.168.1.41
PING 192.168.1.41 (192.168.1.41) 56(84) bytes of data.
64 bytes from 192.168.1.41: icmp_seq=1 ttl=255 time=0.280 ms
64 bytes from 192.168.1.41: icmp_seq=2 ttl=255 time=0.331 ms
64 bytes from 192.168.1.41: icmp_seq=3 ttl=255 time=0.315 ms
...

[root@dhcp-10-163-105-238 network-scripts]# ping 192.168.1.41
PING 192.168.1.41 (192.168.1.41) 56(84) bytes of data.
64 bytes from 192.168.1.41: icmp_seq=1 ttl=255 time=0.280 ms
64 bytes from 192.168.1.41: icmp_seq=2 ttl=255 time=0.331 ms
64 bytes from 192.168.1.41: icmp_seq=3 ttl=255 time=0.315 ms
...

Though, I cannot ping any of the adresses in the MCH "getting started" guide:

[root@dhcp-10-163-105-238 network-scripts]# ping 192.168.1.230
PING 192.168.1.230 (192.168.1.230) 56(84) bytes of data.
^C
--- 192.168.1.230 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

[root@dhcp-10-163-105-238 network-scripts]# ping 192.168.1.231
PING 192.168.1.231 (192.168.1.231) 56(84) bytes of data.
^C
--- 192.168.1.231 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

[root@dhcp-10-163-105-238 network-scripts]# ping 192.168.16.17
PING 192.168.16.17 (192.168.16.17) 56(84) bytes of data.
^C
--- 192.168.16.17 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

[root@dhcp-10-163-105-238 network-scripts]#

[root@dhcp-10-163-105-238 network-scripts]# ping 192.168.1.230
PING 192.168.1.230 (192.168.1.230) 56(84) bytes of data.
^C
--- 192.168.1.230 ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 999ms

[root@dhcp-10-163-105-238 network-scripts]# ping 192.168.1.231
PING 192.168.1.231 (192.168.1.231) 56(84) bytes of data.
^C
--- 192.168.1.231 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

[root@dhcp-10-163-105-238 network-scripts]# ping 192.168.16.17
PING 192.168.16.17 (192.168.16.17) 56(84) bytes of data.
^C
--- 192.168.16.17 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

[root@dhcp-10-163-105-238 network-scripts]#

20/02/2024 01:34

I tried following further steps in Tim's notes:
particularly

3)  SET LINK TO AMC13
cd /home/daq/DAQ/amc13/amc13StandaloneMAN_2014-05-12
source uhalEnv.sh
#set ip addresses in amc13
amc13Config/applyConfig.py  -n 33
Applying IP addresses to board in slot 13 from host 192.168.1.41

#initially got message below - problem was amc13 not seated properly
Unable to send RAW commaQnd (channel=0x7 netfn=0x32 lun=0x0 cmd=0x33
rsp=0xc3): Timeout

3)  SET LINK TO AMC13
cd /home/daq/DAQ/amc13/amc13StandaloneMAN_2014-05-12
source uhalEnv.sh
#set ip addresses in amc13
amc13Config/applyConfig.py  -n 33
Applying IP addresses to board in slot 13 from host 192.168.1.41

#initially got message below - problem was amc13 not seated properly
Unable to send RAW commaQnd (channel=0x7 netfn=0x32 lun=0x0 cmd=0x33
rsp=0xc3): Timeout

I had to hardcode these lines:

#host = options.host
host = "192.168.1.41"

#host = options.host
host = "192.168.1.41"

Because it was detector the "wrong" IP:

[root@dhcp-10-163-105-238 amc13StandaloneMAN_2014-05-12]# amc13Config/applyConfig.py  -n 33
Applying IP addresses to board in slot 13 from host 192.168.1.230
Setting IP addresses using SN 33
Error: Unable to establish LAN session
Error: Unable to establish IPMI v1.5 / RMCP session
Error: Unable to establish LAN session
Error: Unable to establish IPMI v1.5 / RMCP session

[root@dhcp-10-163-105-238 amc13StandaloneMAN_2014-05-12]# amc13Config/applyConfig.py  -n 33
Applying IP addresses to board in slot 13 from host 192.168.1.230
Setting IP addresses using SN 33
Error: Unable to establish LAN session
Error: Unable to establish IPMI v1.5 / RMCP session
Error: Unable to establish LAN session
Error: Unable to establish IPMI v1.5 / RMCP session

(Curiously enough, this is the "correct" IP in the "MCH getting started" guide. I don't know how this IP was picked, somehow an imported class has the information).

That got me further, but I have the same issue as Tim described:

[root@dhcp-10-163-105-238 amc13StandaloneMAN_2014-05-12]# amc13Config/applyConfig.py  -n 33
Applying IP addresses to board in slot 13 from host 192.168.1.41
Setting IP addresses using SN 33
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x33)
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x33)

[root@dhcp-10-163-105-238 amc13StandaloneMAN_2014-05-12]# amc13Config/applyConfig.py  -n 33
Applying IP addresses to board in slot 13 from host 192.168.1.41
Setting IP addresses using SN 33
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x33)
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x33)

So I tried reseating both the AMC and MCH, with no luck.

20/02/2024 01:38

Really what I want to do is ssh into the MCH so I can follow the steps Lawrence gave. However, because we have a different module, I'm unsure how to do that. sshing into the one address I can ping gives:

[root@dhcp-10-163-105-238 amc13StandaloneMAN_2014-05-12]# ssh root@192.168.1.41
ssh: connect to host 192.168.1.41 port 22: Connection refused

[root@dhcp-10-163-105-238 amc13StandaloneMAN_2014-05-12]# ssh root@192.168.1.41
ssh: connect to host 192.168.1.41 port 22: Connection refused

I'm not sure there is a version of linux running on our MCH because the model is different.

20/02/2024 15:43

Tried following this manual
https://nateurope.com/wp-content/uploads/2022/09/NAT-MCH_UsersManual.pdf
to enable sshing into the MCH.

In particular page 37-38 claims I should be able to edit this in the global settings. However, I am never prompted with the option:

[root@dhcp-10-163-105-238 ~]# telnet 192.168.1.41
Trying 192.168.1.41...
Connected to 192.168.1.41.
Escape character is '^]'.


Welcome to NAT-MCH

nat> mchcfg
MCH_CFG: ERR - unknown configuration mode 1312904301
MCH CFG: configuration modes
  [ 0] no action
  [ 1] print complete configuration
  [ 2] reset to defaults
  [ 3] modify MCH global configuration
  [ 4] modify ShM configuration
  [ 5] modify CM configuration
  [ 6] modify SEL configuration
  [ 7] modify GbE switch configuration
  [10] modify NTP configuration
  [11] modify DHCP configuration
  [ ?] print menu
  [ h] print menu
  [ q] quit and save configuration
Enter configuration mode (RET=0/0x0): 3
MCH global parameter:
---------------------
remote interfaces:
  RMCP access:                         enabled
  telnet access:                       enabled
  WEB access:                          enabled
IP address source Mgmt:                board configuration
RMCP session activity timeout minutes: 0 min
RMCP session activity timeout seconds: 60 sec
default fan level:                     30 percent
MCH configuration flags:
  Enable backward compatibility V2.4:  no
  Enable alternative cooling scheme:   no
  Control rear transition module fans: no

MCH remote interfaces
Enable RMCP access (y/n) (RET=y): y
Enable telnet access (y/n) (RET=y): y
Enable WEB access (y/n) (RET=y): y
MCH IP address source:
  no IP address:            0
  board configuration:      1
  DHCP:                     2
  ShM IP link record:       3
  CM IP link record:        4
Enter IP address source Mgmt (dec) (RET=1/0x1): 1
Enter session activity timeout (dec, minutes) (RET=0/0x0): 0
Enter session activity timeout (dec, seconds) (RET=60/0x3c): 60
Enter default fan level (dec, percent) (RET=30/0x1e): 30
MCH configuration flags:
Enable backward compatibility V2.4 (y/n) (RET=n): n
Enable alternative cooling scheme (y/n) (RET=n): n
Control rear transition module fans (y/n) (RET=n): n

Enter configuration mode (RET=0/0x0):

[root@dhcp-10-163-105-238 ~]# telnet 192.168.1.41
Trying 192.168.1.41...
Connected to 192.168.1.41.
Escape character is '^]'.


Welcome to NAT-MCH

nat> mchcfg
MCH_CFG: ERR - unknown configuration mode 1312904301
MCH CFG: configuration modes
  [ 0] no action
  [ 1] print complete configuration
  [ 2] reset to defaults
  [ 3] modify MCH global configuration
  [ 4] modify ShM configuration
  [ 5] modify CM configuration
  [ 6] modify SEL configuration
  [ 7] modify GbE switch configuration
  [10] modify NTP configuration
  [11] modify DHCP configuration
  [ ?] print menu
  [ h] print menu
  [ q] quit and save configuration
Enter configuration mode (RET=0/0x0): 3
MCH global parameter:
---------------------
remote interfaces:
  RMCP access:                         enabled
  telnet access:                       enabled
  WEB access:                          enabled
IP address source Mgmt:                board configuration
RMCP session activity timeout minutes: 0 min
RMCP session activity timeout seconds: 60 sec
default fan level:                     30 percent
MCH configuration flags:
  Enable backward compatibility V2.4:  no
  Enable alternative cooling scheme:   no
  Control rear transition module fans: no

MCH remote interfaces
Enable RMCP access (y/n) (RET=y): y
Enable telnet access (y/n) (RET=y): y
Enable WEB access (y/n) (RET=y): y
MCH IP address source:
  no IP address:            0
  board configuration:      1
  DHCP:                     2
  ShM IP link record:       3
  CM IP link record:        4
Enter IP address source Mgmt (dec) (RET=1/0x1): 1
Enter session activity timeout (dec, minutes) (RET=0/0x0): 0
Enter session activity timeout (dec, seconds) (RET=60/0x3c): 60
Enter default fan level (dec, percent) (RET=30/0x1e): 30
MCH configuration flags:
Enable backward compatibility V2.4 (y/n) (RET=n): n
Enable alternative cooling scheme (y/n) (RET=n): n
Control rear transition module fans (y/n) (RET=n): n

Enter configuration mode (RET=0/0x0):

The guide has this written a few times:

2.2.5 Console Port – USB / Telnet / SSH
The console port provides an interface to the Command Line Interface (CLI) of the onboard
CPU. The console interface can be used to set the operational and configuration parameters of
the NAT-MCH.
Once the IP configuration has been set, the console interface can be switched to a Telnet or
SSH session by connecting via Telnet/SSH. In case a password had been configured for a Telnet
session, a check of this password is done when starting the Telnet session. For SSH sessions
this password check is mandatory.
For details regarding configuration of a Telnet/SSH password, please refer to chapter 8
“Command line interface”.

So I checked Chapter 8 and tried running this commnad:

ip
IP configuration: Configures IP addresses, net mask, broadcast address, and gateway.

But it doesn't appear to do anything:

nat> ip
MCH_CFG: ERR - unknown configuration mode 1312904297
MCH CFG: configuration modes
  [ 0] no action
  [ 1] print complete configuration
  [ 2] reset to defaults
  [ 3] modify MCH global configuration
  [ 4] modify ShM configuration
  [ 5] modify CM configuration
  [ 6] modify SEL configuration
  [ 7] modify GbE switch configuration
  [10] modify NTP configuration
  [11] modify DHCP configuration
  [ ?] print menu
  [ h] print menu
  [ q] quit and save configuration
Enter configuration mode (RET=0/0x0):

nat> ip
MCH_CFG: ERR - unknown configuration mode 1312904297
MCH CFG: configuration modes
  [ 0] no action
  [ 1] print complete configuration
  [ 2] reset to defaults
  [ 3] modify MCH global configuration
  [ 4] modify ShM configuration
  [ 5] modify CM configuration
  [ 6] modify SEL configuration
  [ 7] modify GbE switch configuration
  [10] modify NTP configuration
  [11] modify DHCP configuration
  [ ?] print menu
  [ h] print menu
  [ q] quit and save configuration
Enter configuration mode (RET=0/0x0):

20/02/2024 16:21

Tried changing network script for the 10GbE ports to look more like the one we used to connect to the MCH
Port 1:

#
# Connect to AMC
#
TYPE=Ethernet
BOOTPROTO=static
IPADDR=192.168.1.2
NETMASK=255.255.0.0
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=enp1s0f0
DEVICE=enp1s0f0
ONBOOT=yes

#
# Connect to AMC
#
TYPE=Ethernet
BOOTPROTO=static
IPADDR=192.168.1.2
NETMASK=255.255.0.0
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=enp1s0f0
DEVICE=enp1s0f0
ONBOOT=yes

Port 2:

#
# Connect to AMC
#
TYPE=Ethernet
BOOTPROTO=static
IPADDR=192.168.1.3
NETMASK=255.255.0.0
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=enp1s0f1
DEVICE=enp1s0f1
ONBOOT=yes

#
# Connect to AMC
#
TYPE=Ethernet
BOOTPROTO=static
IPADDR=192.168.1.3
NETMASK=255.255.0.0
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=enp1s0f1
DEVICE=enp1s0f1
ONBOOT=yes

did

ifdown enp1s0f0
ifdown enp1s0f1
ifup enp1s0f0
ifup enp1s0f1

ifdown enp1s0f0
ifdown enp1s0f1
ifup enp1s0f0
ifup enp1s0f1

But got no further, still get the same error:

[root@dhcp-10-163-105-238 amc13StandaloneMAN_2014-05-12]# amc13Config/applyConfig.py  -n 33
Applying IP addresses to board in slot 13 from host 192.168.1.41
Setting IP addresses using SN 33
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x33)
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x33)

[root@dhcp-10-163-105-238 amc13StandaloneMAN_2014-05-12]# amc13Config/applyConfig.py  -n 33
Applying IP addresses to board in slot 13 from host 192.168.1.41
Setting IP addresses using SN 33
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x33)
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x33)

20/02/2024 16:24

I realized that this curiosity I had

(Curiously enough, this is the "correct" IP in the "MCH getting started" guide. I don't know how this IP was picked, somehow an imported class has the information).

Is picked in the file amc13Config/systemVars.py. So I wrote the correct IP in this file and undid my edits to amc13Config/applyConfig.py.

22/02/2024 01:12

I noticed whenever I use the development board "PCI Express" IP block (really a PCIe block with AXI interface for DDR3) I get the following warning:
WARNING: [IP_Flow 19-3374] An attempt to modify the value of disabled parameter 'Xlnx_Ref_Board' from 'None' to 'NEREID' has been ignored for IP 'design_1_xdma_0_0/design_1_xdma_0_0_pcie2_ip
It doesn't stop validation, bitstream generation, or anything else.

22/02/2024 01:40

Tried a design that is just the development boards "PCI Express" block. I ran block automation and there was no option for connection automation (everything was connected).
I had 2 warnings I ignored:

"WARNING: [BD 41-2670] Found an incomplete address path from address space '/xdma_0/M_AXI' to master interface '/xdma_0/M_AXI'. Please either complete or remove this path to resolve."
WARNING: [IP_Flow 19-3374] An attempt to modify the value of disabled parameter 'Xlnx_Ref_Board' from 'None' to 'NEREID' has been ignored for IP 'design_1_xdma_0_0/design_1_xdma_0_0_pcie2_ip

But I was still able to generate a bitstream and program the board's flash memory with the generated .bin file.
I was unable to see the board with lspci or lspci -vv on the 'fe01' computer.

22/02/2024 01:47

I tried making a block design using Vivado's "7 Series Integrated Block for PCI Express." I couldn't even get a valid design. I tried running connection automation after configuring the block as described in https://numato.com/kb/getting-started-with-pci-express-on-nereid/. Instead of generating an example project, I just tried to run the connection automation instead. I don't know how to resolve this critical warning

CRITICAL WARNING: [BD 41-759] The input pins (listed below) are either not connected or do not have a source port, and they don't have a tie-off specified. These pins are tied-off to all 0's to avoid error in Implementation flow.
Please check your design and connect them as needed: 
/pcie_7x_0/s_axis_tx_tvalid
/pcie_7x_0/sys_rst_n

CRITICAL WARNING: [BD 41-759] The input pins (listed below) are either not connected or do not have a source port, and they don't have a tie-off specified. These pins are tied-off to all 0's to avoid error in Implementation flow.
Please check your design and connect them as needed: 
/pcie_7x_0/s_axis_tx_tvalid
/pcie_7x_0/sys_rst_n

I.e. I don't know what to put into the input pins. I especially don't know what to put into the output pins.
I have the same problem trying to insert the block into our working microblazer design.

22/02/2024 02:21

In the product guide for the 7 Series Integrated Block for PCI Express Product Guide (PG054) (https://docs.xilinx.com/r/en-US/pg054-7series-pcie/Minimum-Device-Requirements) I noticed this line:

Kintex-7 FBG484 package supports only x1, x2, and x4 operation; x8 is not supported.

This seems to suggest this block will NOT work for out HTGK700 board, at least not utilzing all 8 lanes.

22/02/2024 02:39

After skipping through 7 Series Integrated Block for PCI Express Product Guide (PG054) (https://docs.xilinx.com/r/en-US/pg054-7series-pcie), I realized there's not much in there that can help us with this block.

My goal was to figure out how to 'wire up' the block becuase I know what the "names" of the "pcie invovled" pins are from the board configuration files ( you can find that here https://github.com/numato/vivadoBSP/blob/main/NereidDevBoard7K160T/3.0/part0_pins.xml, below is a snippet):

    <pin index="181" name ="pcie_mgt_clkn" loc="K5"/>
    <pin index="182" name ="pcie_mgt_clkp" loc="K6"/>
    <pin index="183" name ="pcie_perstn_rst" iostandard="LVCMOS33" loc="E21"/>
    <pin index="184" name ="pcie_rx0_n" loc="J4"/>
    <pin index="185" name ="pcie_rx1_n" loc="L4"/>
    <pin index="186" name ="pcie_rx2_n" loc="N4"/>
    <pin index="187" name ="pcie_rx3_n" loc="R4"/>
    
    <pin index="188" name ="pcie_rx0_p" loc="J3"/>
    <pin index="189" name ="pcie_rx1_p" loc="L3"/>
    <pin index="190" name ="pcie_rx2_p" loc="N3"/>
    <pin index="191" name ="pcie_rx3_p" loc="R3"/>
 
    <pin index="192" name ="pcie_tx0_n" loc="H2"/>
    <pin index="193" name ="pcie_tx1_n" loc="K2"/>
    <pin index="194" name ="pcie_tx2_n" loc="M2"/>
    <pin index="195" name ="pcie_tx3_n" loc="P2"/>
    
    <pin index="196" name ="pcie_tx0_p" loc="H1"/>
    <pin index="197" name ="pcie_tx1_p" loc="K1"/>
    <pin index="198" name ="pcie_tx2_p" loc="M1"/>
    <pin index="199" name ="pcie_tx3_p" loc="P1"/>

    <pin index="181" name ="pcie_mgt_clkn" loc="K5"/>
    <pin index="182" name ="pcie_mgt_clkp" loc="K6"/>
    <pin index="183" name ="pcie_perstn_rst" iostandard="LVCMOS33" loc="E21"/>
    <pin index="184" name ="pcie_rx0_n" loc="J4"/>
    <pin index="185" name ="pcie_rx1_n" loc="L4"/>
    <pin index="186" name ="pcie_rx2_n" loc="N4"/>
    <pin index="187" name ="pcie_rx3_n" loc="R4"/>
    
    <pin index="188" name ="pcie_rx0_p" loc="J3"/>
    <pin index="189" name ="pcie_rx1_p" loc="L3"/>
    <pin index="190" name ="pcie_rx2_p" loc="N3"/>
    <pin index="191" name ="pcie_rx3_p" loc="R3"/>
 
    <pin index="192" name ="pcie_tx0_n" loc="H2"/>
    <pin index="193" name ="pcie_tx1_n" loc="K2"/>
    <pin index="194" name ="pcie_tx2_n" loc="M2"/>
    <pin index="195" name ="pcie_tx3_n" loc="P2"/>
    
    <pin index="196" name ="pcie_tx0_p" loc="H1"/>
    <pin index="197" name ="pcie_tx1_p" loc="K1"/>
    <pin index="198" name ="pcie_tx2_p" loc="M1"/>
    <pin index="199" name ="pcie_tx3_p" loc="P1"/>

But I didn't see anything that helped me in that regard

22/02/2024 16:23

Plugging in an FC7 and WFD5 I am able to see the components appear over telnet in the crate

IDB: print found devices
----------------------------------------------
FRU   type  i2c state sensors name
----------------------------------------------
  0   MCH1   20   M4     64   NMCH-CM
  3   MCH1   10   M4     12   NAT-MCH-MCMC
 13   AMC9   82   M4     31   ICL-CERN FC7
 15   AMC11   86   M4     11   CU WFD5
 30   AMC26   a4   M4      9   BU AMC13
 40    CU1   a8   M4     22   VT VT095
 41    CU2   aa   M4     19   VT VT095
 50    PM1   c2   M4     39   VT UTC010
128  ShMC1   00   M0      0   <none>
253 ShFRU1   f4   M0      0   <Carrier FRU>
254 ShFRU1   f4   M0      0   <Shelf FRU>
----------------------------------------------
  found 11 devices

IDB: print found devices
----------------------------------------------
FRU   type  i2c state sensors name
----------------------------------------------
  0   MCH1   20   M4     64   NMCH-CM
  3   MCH1   10   M4     12   NAT-MCH-MCMC
 13   AMC9   82   M4     31   ICL-CERN FC7
 15   AMC11   86   M4     11   CU WFD5
 30   AMC26   a4   M4      9   BU AMC13
 40    CU1   a8   M4     22   VT VT095
 41    CU2   aa   M4     19   VT VT095
 50    PM1   c2   M4     39   VT UTC010
128  ShMC1   00   M0      0   <none>
253 ShFRU1   f4   M0      0   <Carrier FRU>
254 ShFRU1   f4   M0      0   <Shelf FRU>
----------------------------------------------
  found 11 devices

22/02/2024 16:54

After installing the lxedaq branch and using the "updated" software as Lawrence suggested in his email, I'm still unable to read any IPs of the modules:

Hi Tim,

I never see that light on the AMC13 working. THere’s probably some bug with that version of the MMC firmware.

THere are python scripts that use IPMI to read / set the IP addresses. I finally figured out how to get the amc13_v1_2_18 files to appear properly in git. I’ve done this in the lxedaq branch. Do a pull, check that one out, and then have a look in

gm2daq-modified/amc13/amc13_v1_2_18/dev_tools/amc13Config/

You will want readIPs.py to read the current IP addresses, and storeConfig.py to get those addresses into the PROM. I believe you want to use the -v options with the 192.168.xx.13 address, and it will automatically add 1 for the 2nd IP address. You will either want to power cycle the AMC13 payload power or use the applyConfig.py script to make the IP addresses current.

-Lawrence

First I checked systemVars.py:

[root@dhcp-10-163-105-238 amc13Config]# cat systemVars.py

#File to specify what the default varaibles addresses are used in your system

#Default IP address for commercial MCH module
# our NAT MCH address
DEFAULT_HOST_IP="192.168.1.41"
# our Vadatech MCH address
# DEFAULT_HOST_IP="192.168.1.2"

#Default AMC13 slot number
DEFAULT_AMC13_SLOT=9

#Location of 'config_tools'. This should never need to be changed
DEFAULT_CONFIG_DIR="./config_tools"

#Network base for your uTCA crate's AMC modules
NETWORK_BASE="192.168.1"

[root@dhcp-10-163-105-238 amc13Config]# cat systemVars.py

#File to specify what the default varaibles addresses are used in your system

#Default IP address for commercial MCH module
# our NAT MCH address
DEFAULT_HOST_IP="192.168.1.41"
# our Vadatech MCH address
# DEFAULT_HOST_IP="192.168.1.2"

#Default AMC13 slot number
DEFAULT_AMC13_SLOT=9

#Location of 'config_tools'. This should never need to be changed
DEFAULT_CONFIG_DIR="./config_tools"

#Network base for your uTCA crate's AMC modules
NETWORK_BASE="192.168.1"

Everything look reasonable here, so then I sourced this script to set the environment:

[root@dhcp-10-163-105-238 amc13_v1_2_18]# cat env.sh
if [[ $_ == $0 ]]; then
  echo "$0 is meant to be sourced:"
  echo "  source $0"
  exit 0
fi

AMC13_STANDALONE_ROOT=$( readlink -f $(dirname $BASH_SOURCE)/ )
CACTUS_ROOT=/opt/cactus

PATH="${AMC13_STANDALONE_ROOT}/tools/bin:${PATH}"

PYTHONPATH="${AMC13_STANDALONE_ROOT}/python/pkg:${PYTHONPATH}"

LD_LIBRARY_PATH="${CACTUS_ROOT}/lib/:${LD_LIBRARY_PATH}"
LD_LIBRARY_PATH="${AMC13_STANDALONE_ROOT}/amc13/lib/:${LD_LIBRARY_PATH}"
LD_LIBRARY_PATH="${AMC13_STANDALONE_ROOT}/tools/lib/:${LD_LIBRARY_PATH}"

export AMC13_STANDALONE_ROOT CACTUS_ROOT PATH LD_LIBRARY_PATH PYTHONPATH

[root@dhcp-10-163-105-238 amc13_v1_2_18]# cat env.sh
if [[ $_ == $0 ]]; then
  echo "$0 is meant to be sourced:"
  echo "  source $0"
  exit 0
fi

AMC13_STANDALONE_ROOT=$( readlink -f $(dirname $BASH_SOURCE)/ )
CACTUS_ROOT=/opt/cactus

PATH="${AMC13_STANDALONE_ROOT}/tools/bin:${PATH}"

PYTHONPATH="${AMC13_STANDALONE_ROOT}/python/pkg:${PYTHONPATH}"

LD_LIBRARY_PATH="${CACTUS_ROOT}/lib/:${LD_LIBRARY_PATH}"
LD_LIBRARY_PATH="${AMC13_STANDALONE_ROOT}/amc13/lib/:${LD_LIBRARY_PATH}"
LD_LIBRARY_PATH="${AMC13_STANDALONE_ROOT}/tools/lib/:${LD_LIBRARY_PATH}"

export AMC13_STANDALONE_ROOT CACTUS_ROOT PATH LD_LIBRARY_PATH PYTHONPATH

For good luck I also ran:

export AMC13_SERIAL_NO=33

export AMC13_SERIAL_NO=33

The output of trying to read IPs of the modules in the crate is the same as before:

[root@dhcp-10-163-105-238 amc13Config]# ./readIPs.py --slot=13
Reading IP addresses of board in slot 13 from host 192.168.1.41
T2 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0xa4 raw 0x32 0x34 0 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]
T1 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0xa4 raw 0x32 0x34 1 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]
[root@dhcp-10-163-105-238 amc13Config]# ./readIPs.py --slot=11
Reading IP addresses of board in slot 11 from host 192.168.1.41
T2 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0x86 raw 0x32 0x34 0 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]
T1 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0x86 raw 0x32 0x34 1 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]
[root@dhcp-10-163-105-238 amc13Config]# ./readIPs.py --slot=9
Reading IP addresses of board in slot 9 from host 192.168.1.41
T2 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0x82 raw 0x32 0x34 0 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]
T1 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0x82 raw 0x32 0x34 1 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]

[root@dhcp-10-163-105-238 amc13Config]# ./readIPs.py --slot=13
Reading IP addresses of board in slot 13 from host 192.168.1.41
T2 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0xa4 raw 0x32 0x34 0 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]
T1 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0xa4 raw 0x32 0x34 1 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]
[root@dhcp-10-163-105-238 amc13Config]# ./readIPs.py --slot=11
Reading IP addresses of board in slot 11 from host 192.168.1.41
T2 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0x86 raw 0x32 0x34 0 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]
T1 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0x86 raw 0x32 0x34 1 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]
[root@dhcp-10-163-105-238 amc13Config]# ./readIPs.py --slot=9
Reading IP addresses of board in slot 9 from host 192.168.1.41
T2 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0x82 raw 0x32 0x34 0 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]
T1 IP Bytes:
ipmitool -H 192.168.1.41 -U '' -P '' -T 0x82 -b 7 -t 0x82 raw 0x32 0x34 1 11 0 4
Unable to send RAW command (channel=0x7 netfn=0x32 lun=0x0 cmd=0x34)
[]
[]

22/02/2024 17:08

I ran a brute force check where I ping every IP on the network I expect the modules to live (192.162.1.xxx)

[root@dhcp-10-163-105-238 shell_scripts]# cat brute_force_ping_check.sh
#!/bin/bash

# Define colors
GREEN='\033[0;32m'
NC='\033[0m' # No Color

# Define the IP range
IP_PREFIX="192.168.1."

# Loop through each IP address and ping it with a 1 second timeout
for ((i=1; i<=255; i++))
do
    IP="${IP_PREFIX}${i}"
    if ping -c 1 -W 1 $IP &> /dev/null; then
        echo -e "${GREEN}Host $IP is up${NC}"
    else
        echo "Host $IP is down"
    fi
done

[root@dhcp-10-163-105-238 shell_scripts]# cat brute_force_ping_check.sh
#!/bin/bash

# Define colors
GREEN='\033[0;32m'
NC='\033[0m' # No Color

# Define the IP range
IP_PREFIX="192.168.1."

# Loop through each IP address and ping it with a 1 second timeout
for ((i=1; i<=255; i++))
do
    IP="${IP_PREFIX}${i}"
    if ping -c 1 -W 1 $IP &> /dev/null; then
        echo -e "${GREEN}Host $IP is up${NC}"
    else
        echo "Host $IP is down"
    fi
done

The results are that I can only ping the computer itself and the MCH, not other modules were found.

[root@dhcp-10-163-105-238 shell_scripts]# ./brute_force_ping_check.sh
Host 192.168.1.1 is up
Host 192.168.1.2 is down
Host 192.168.1.3 is down
Host 192.168.1.4 is down
Host 192.168.1.5 is down
Host 192.168.1.6 is down
Host 192.168.1.7 is down
Host 192.168.1.8 is down
Host 192.168.1.9 is down
Host 192.168.1.10 is down
Host 192.168.1.11 is down
Host 192.168.1.12 is down
Host 192.168.1.13 is down
Host 192.168.1.14 is down
Host 192.168.1.15 is down
Host 192.168.1.16 is down
Host 192.168.1.17 is down
Host 192.168.1.18 is down
Host 192.168.1.19 is down
Host 192.168.1.20 is down
Host 192.168.1.21 is down
Host 192.168.1.22 is down
Host 192.168.1.23 is down
Host 192.168.1.24 is down
Host 192.168.1.25 is down
Host 192.168.1.26 is down
Host 192.168.1.27 is down
Host 192.168.1.28 is down
Host 192.168.1.29 is down
Host 192.168.1.30 is down
Host 192.168.1.31 is down
Host 192.168.1.32 is down
Host 192.168.1.33 is down
Host 192.168.1.34 is down
Host 192.168.1.35 is down
Host 192.168.1.36 is down
Host 192.168.1.37 is down
Host 192.168.1.38 is down
Host 192.168.1.39 is down
Host 192.168.1.40 is down
Host 192.168.1.41 is up
Host 192.168.1.42 is down
Host 192.168.1.43 is down
Host 192.168.1.44 is down
Host 192.168.1.45 is down
Host 192.168.1.46 is down
Host 192.168.1.47 is down
Host 192.168.1.48 is down
Host 192.168.1.49 is down
Host 192.168.1.50 is down
Host 192.168.1.51 is down
Host 192.168.1.52 is down
Host 192.168.1.53 is down
Host 192.168.1.54 is down
Host 192.168.1.55 is down
Host 192.168.1.56 is down
Host 192.168.1.57 is down
Host 192.168.1.58 is down
Host 192.168.1.59 is down
Host 192.168.1.60 is down
Host 192.168.1.61 is down
Host 192.168.1.62 is down
Host 192.168.1.63 is down
Host 192.168.1.64 is down
Host 192.168.1.65 is down
Host 192.168.1.66 is down
Host 192.168.1.67 is down
Host 192.168.1.68 is down
Host 192.168.1.69 is down
Host 192.168.1.70 is down
Host 192.168.1.71 is down
Host 192.168.1.72 is down
Host 192.168.1.73 is down
Host 192.168.1.74 is down
Host 192.168.1.75 is down
Host 192.168.1.76 is down
Host 192.168.1.77 is down
Host 192.168.1.78 is down
Host 192.168.1.79 is down
Host 192.168.1.80 is down
Host 192.168.1.81 is down
Host 192.168.1.82 is down
Host 192.168.1.83 is down
Host 192.168.1.84 is down
Host 192.168.1.85 is down
Host 192.168.1.86 is down
Host 192.168.1.87 is down
Host 192.168.1.88 is down
Host 192.168.1.89 is down
Host 192.168.1.90 is down
Host 192.168.1.91 is down
Host 192.168.1.92 is down
Host 192.168.1.93 is down
Host 192.168.1.94 is down
Host 192.168.1.95 is down
Host 192.168.1.96 is down
Host 192.168.1.97 is down
Host 192.168.1.98 is down
Host 192.168.1.99 is down
Host 192.168.1.100 is down
Host 192.168.1.101 is down
Host 192.168.1.102 is down
Host 192.168.1.103 is down
Host 192.168.1.104 is down
Host 192.168.1.105 is down
Host 192.168.1.106 is down
Host 192.168.1.107 is down
Host 192.168.1.108 is down
Host 192.168.1.109 is down
Host 192.168.1.110 is down
Host 192.168.1.111 is down
Host 192.168.1.112 is down
Host 192.168.1.113 is down
Host 192.168.1.114 is down
Host 192.168.1.115 is down
Host 192.168.1.116 is down
Host 192.168.1.117 is down
Host 192.168.1.118 is down
Host 192.168.1.119 is down
Host 192.168.1.120 is down
Host 192.168.1.121 is down
Host 192.168.1.122 is down
Host 192.168.1.123 is down
Host 192.168.1.124 is down
Host 192.168.1.125 is down
Host 192.168.1.126 is down
Host 192.168.1.127 is down
Host 192.168.1.128 is down
Host 192.168.1.129 is down
Host 192.168.1.130 is down
Host 192.168.1.131 is down
Host 192.168.1.132 is down
Host 192.168.1.133 is down
Host 192.168.1.134 is down
Host 192.168.1.135 is down
Host 192.168.1.136 is down
Host 192.168.1.137 is down
Host 192.168.1.138 is down
Host 192.168.1.139 is down
Host 192.168.1.140 is down
Host 192.168.1.141 is down
Host 192.168.1.142 is down
Host 192.168.1.143 is down
Host 192.168.1.144 is down
Host 192.168.1.145 is down
Host 192.168.1.146 is down
Host 192.168.1.147 is down
Host 192.168.1.148 is down
Host 192.168.1.149 is down
Host 192.168.1.150 is down
Host 192.168.1.151 is down
Host 192.168.1.152 is down
Host 192.168.1.153 is down
Host 192.168.1.154 is down
Host 192.168.1.155 is down
Host 192.168.1.156 is down
Host 192.168.1.157 is down
Host 192.168.1.158 is down
Host 192.168.1.159 is down
Host 192.168.1.160 is down
Host 192.168.1.161 is down
Host 192.168.1.162 is down
Host 192.168.1.163 is down
Host 192.168.1.164 is down
Host 192.168.1.165 is down
Host 192.168.1.166 is down
Host 192.168.1.167 is down
Host 192.168.1.168 is down
Host 192.168.1.169 is down
Host 192.168.1.170 is down
Host 192.168.1.171 is down
Host 192.168.1.172 is down
Host 192.168.1.173 is down
Host 192.168.1.174 is down
Host 192.168.1.175 is down
Host 192.168.1.176 is down
Host 192.168.1.177 is down
Host 192.168.1.178 is down
Host 192.168.1.179 is down
Host 192.168.1.180 is down
Host 192.168.1.181 is down
Host 192.168.1.182 is down
Host 192.168.1.183 is down
Host 192.168.1.184 is down
Host 192.168.1.185 is down
Host 192.168.1.186 is down
Host 192.168.1.187 is down
Host 192.168.1.188 is down
Host 192.168.1.189 is down
Host 192.168.1.190 is down
Host 192.168.1.191 is down
Host 192.168.1.192 is down
Host 192.168.1.193 is down
Host 192.168.1.194 is down
Host 192.168.1.195 is down
Host 192.168.1.196 is down
Host 192.168.1.197 is down
Host 192.168.1.198 is down
Host 192.168.1.199 is down
Host 192.168.1.200 is down
Host 192.168.1.201 is down
Host 192.168.1.202 is down
Host 192.168.1.203 is down
Host 192.168.1.204 is down
Host 192.168.1.205 is down
Host 192.168.1.206 is down
Host 192.168.1.207 is down
Host 192.168.1.208 is down
Host 192.168.1.209 is down
Host 192.168.1.210 is down
Host 192.168.1.211 is down
Host 192.168.1.212 is down
Host 192.168.1.213 is down
Host 192.168.1.214 is down
Host 192.168.1.215 is down
Host 192.168.1.216 is down
Host 192.168.1.217 is down
Host 192.168.1.218 is down
Host 192.168.1.219 is down
Host 192.168.1.220 is down
Host 192.168.1.221 is down
Host 192.168.1.222 is down
Host 192.168.1.223 is down
Host 192.168.1.224 is down
Host 192.168.1.225 is down
Host 192.168.1.226 is down
Host 192.168.1.227 is down
Host 192.168.1.228 is down
Host 192.168.1.229 is down
Host 192.168.1.230 is down
Host 192.168.1.231 is down
Host 192.168.1.232 is down
Host 192.168.1.233 is down
Host 192.168.1.234 is down
Host 192.168.1.235 is down
Host 192.168.1.236 is down
Host 192.168.1.237 is down
Host 192.168.1.238 is down
Host 192.168.1.239 is down
Host 192.168.1.240 is down
Host 192.168.1.241 is down
Host 192.168.1.242 is down
Host 192.168.1.243 is down
Host 192.168.1.244 is down
Host 192.168.1.245 is down
Host 192.168.1.246 is down
Host 192.168.1.247 is down
Host 192.168.1.248 is down
Host 192.168.1.249 is down
Host 192.168.1.250 is down
Host 192.168.1.251 is down
Host 192.168.1.252 is down
Host 192.168.1.253 is down
Host 192.168.1.254 is down
Host 192.168.1.255 is down

[root@dhcp-10-163-105-238 shell_scripts]# ./brute_force_ping_check.sh
Host 192.168.1.1 is up
Host 192.168.1.2 is down
Host 192.168.1.3 is down
Host 192.168.1.4 is down
Host 192.168.1.5 is down
Host 192.168.1.6 is down
Host 192.168.1.7 is down
Host 192.168.1.8 is down
Host 192.168.1.9 is down
Host 192.168.1.10 is down
Host 192.168.1.11 is down
Host 192.168.1.12 is down
Host 192.168.1.13 is down
Host 192.168.1.14 is down
Host 192.168.1.15 is down
Host 192.168.1.16 is down
Host 192.168.1.17 is down
Host 192.168.1.18 is down
Host 192.168.1.19 is down
Host 192.168.1.20 is down
Host 192.168.1.21 is down
Host 192.168.1.22 is down
Host 192.168.1.23 is down
Host 192.168.1.24 is down
Host 192.168.1.25 is down
Host 192.168.1.26 is down
Host 192.168.1.27 is down
Host 192.168.1.28 is down
Host 192.168.1.29 is down
Host 192.168.1.30 is down
Host 192.168.1.31 is down
Host 192.168.1.32 is down
Host 192.168.1.33 is down
Host 192.168.1.34 is down
Host 192.168.1.35 is down
Host 192.168.1.36 is down
Host 192.168.1.37 is down
Host 192.168.1.38 is down
Host 192.168.1.39 is down
Host 192.168.1.40 is down
Host 192.168.1.41 is up
Host 192.168.1.42 is down
Host 192.168.1.43 is down
Host 192.168.1.44 is down
Host 192.168.1.45 is down
Host 192.168.1.46 is down
Host 192.168.1.47 is down
Host 192.168.1.48 is down
Host 192.168.1.49 is down
Host 192.168.1.50 is down
Host 192.168.1.51 is down
Host 192.168.1.52 is down
Host 192.168.1.53 is down
Host 192.168.1.54 is down
Host 192.168.1.55 is down
Host 192.168.1.56 is down
Host 192.168.1.57 is down
Host 192.168.1.58 is down
Host 192.168.1.59 is down
Host 192.168.1.60 is down
Host 192.168.1.61 is down
Host 192.168.1.62 is down
Host 192.168.1.63 is down
Host 192.168.1.64 is down
Host 192.168.1.65 is down
Host 192.168.1.66 is down
Host 192.168.1.67 is down
Host 192.168.1.68 is down
Host 192.168.1.69 is down
Host 192.168.1.70 is down
Host 192.168.1.71 is down
Host 192.168.1.72 is down
Host 192.168.1.73 is down
Host 192.168.1.74 is down
Host 192.168.1.75 is down
Host 192.168.1.76 is down
Host 192.168.1.77 is down
Host 192.168.1.78 is down
Host 192.168.1.79 is down
Host 192.168.1.80 is down
Host 192.168.1.81 is down
Host 192.168.1.82 is down
Host 192.168.1.83 is down
Host 192.168.1.84 is down
Host 192.168.1.85 is down
Host 192.168.1.86 is down
Host 192.168.1.87 is down
Host 192.168.1.88 is down
Host 192.168.1.89 is down
Host 192.168.1.90 is down
Host 192.168.1.91 is down
Host 192.168.1.92 is down
Host 192.168.1.93 is down
Host 192.168.1.94 is down
Host 192.168.1.95 is down
Host 192.168.1.96 is down
Host 192.168.1.97 is down
Host 192.168.1.98 is down
Host 192.168.1.99 is down
Host 192.168.1.100 is down
Host 192.168.1.101 is down
Host 192.168.1.102 is down
Host 192.168.1.103 is down
Host 192.168.1.104 is down
Host 192.168.1.105 is down
Host 192.168.1.106 is down
Host 192.168.1.107 is down
Host 192.168.1.108 is down
Host 192.168.1.109 is down
Host 192.168.1.110 is down
Host 192.168.1.111 is down
Host 192.168.1.112 is down
Host 192.168.1.113 is down
Host 192.168.1.114 is down
Host 192.168.1.115 is down
Host 192.168.1.116 is down
Host 192.168.1.117 is down
Host 192.168.1.118 is down
Host 192.168.1.119 is down
Host 192.168.1.120 is down
Host 192.168.1.121 is down
Host 192.168.1.122 is down
Host 192.168.1.123 is down
Host 192.168.1.124 is down
Host 192.168.1.125 is down
Host 192.168.1.126 is down
Host 192.168.1.127 is down
Host 192.168.1.128 is down
Host 192.168.1.129 is down
Host 192.168.1.130 is down
Host 192.168.1.131 is down
Host 192.168.1.132 is down
Host 192.168.1.133 is down
Host 192.168.1.134 is down
Host 192.168.1.135 is down
Host 192.168.1.136 is down
Host 192.168.1.137 is down
Host 192.168.1.138 is down
Host 192.168.1.139 is down
Host 192.168.1.140 is down
Host 192.168.1.141 is down
Host 192.168.1.142 is down
Host 192.168.1.143 is down
Host 192.168.1.144 is down
Host 192.168.1.145 is down
Host 192.168.1.146 is down
Host 192.168.1.147 is down
Host 192.168.1.148 is down
Host 192.168.1.149 is down
Host 192.168.1.150 is down
Host 192.168.1.151 is down
Host 192.168.1.152 is down
Host 192.168.1.153 is down
Host 192.168.1.154 is down
Host 192.168.1.155 is down
Host 192.168.1.156 is down
Host 192.168.1.157 is down
Host 192.168.1.158 is down
Host 192.168.1.159 is down
Host 192.168.1.160 is down
Host 192.168.1.161 is down
Host 192.168.1.162 is down
Host 192.168.1.163 is down
Host 192.168.1.164 is down
Host 192.168.1.165 is down
Host 192.168.1.166 is down
Host 192.168.1.167 is down
Host 192.168.1.168 is down
Host 192.168.1.169 is down
Host 192.168.1.170 is down
Host 192.168.1.171 is down
Host 192.168.1.172 is down
Host 192.168.1.173 is down
Host 192.168.1.174 is down
Host 192.168.1.175 is down
Host 192.168.1.176 is down
Host 192.168.1.177 is down
Host 192.168.1.178 is down
Host 192.168.1.179 is down
Host 192.168.1.180 is down
Host 192.168.1.181 is down
Host 192.168.1.182 is down
Host 192.168.1.183 is down
Host 192.168.1.184 is down
Host 192.168.1.185 is down
Host 192.168.1.186 is down
Host 192.168.1.187 is down
Host 192.168.1.188 is down
Host 192.168.1.189 is down
Host 192.168.1.190 is down
Host 192.168.1.191 is down
Host 192.168.1.192 is down
Host 192.168.1.193 is down
Host 192.168.1.194 is down
Host 192.168.1.195 is down
Host 192.168.1.196 is down
Host 192.168.1.197 is down
Host 192.168.1.198 is down
Host 192.168.1.199 is down
Host 192.168.1.200 is down
Host 192.168.1.201 is down
Host 192.168.1.202 is down
Host 192.168.1.203 is down
Host 192.168.1.204 is down
Host 192.168.1.205 is down
Host 192.168.1.206 is down
Host 192.168.1.207 is down
Host 192.168.1.208 is down
Host 192.168.1.209 is down
Host 192.168.1.210 is down
Host 192.168.1.211 is down
Host 192.168.1.212 is down
Host 192.168.1.213 is down
Host 192.168.1.214 is down
Host 192.168.1.215 is down
Host 192.168.1.216 is down
Host 192.168.1.217 is down
Host 192.168.1.218 is down
Host 192.168.1.219 is down
Host 192.168.1.220 is down
Host 192.168.1.221 is down
Host 192.168.1.222 is down
Host 192.168.1.223 is down
Host 192.168.1.224 is down
Host 192.168.1.225 is down
Host 192.168.1.226 is down
Host 192.168.1.227 is down
Host 192.168.1.228 is down
Host 192.168.1.229 is down
Host 192.168.1.230 is down
Host 192.168.1.231 is down
Host 192.168.1.232 is down
Host 192.168.1.233 is down
Host 192.168.1.234 is down
Host 192.168.1.235 is down
Host 192.168.1.236 is down
Host 192.168.1.237 is down
Host 192.168.1.238 is down
Host 192.168.1.239 is down
Host 192.168.1.240 is down
Host 192.168.1.241 is down
Host 192.168.1.242 is down
Host 192.168.1.243 is down
Host 192.168.1.244 is down
Host 192.168.1.245 is down
Host 192.168.1.246 is down
Host 192.168.1.247 is down
Host 192.168.1.248 is down
Host 192.168.1.249 is down
Host 192.168.1.250 is down
Host 192.168.1.251 is down
Host 192.168.1.252 is down
Host 192.168.1.253 is down
Host 192.168.1.254 is down
Host 192.168.1.255 is down